Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow sensio/distribution-bundle ^5.0 #77

Merged
merged 3 commits into from
Jan 16, 2017
Merged

Conversation

emodric
Copy link
Collaborator

@emodric emodric commented Jan 12, 2017

composer install works fine with 5.0 too.

`composer install` works fine with 5.0 too.
@emodric
Copy link
Collaborator Author

emodric commented Jan 12, 2017

Huh! ConfigurationDumper still uses \Sensio\Bundle\DistributionBundle\Configurator\Configurator which was removed in 5.0...

It looks like it writes a random secret to app/config/parameters.yml after legacy setup wizard is ran.

I think it's safe to remove it: https://github.com/ezsystems/LegacyBridge/blob/master/bundle/SetupWizard/ConfigurationDumper.php#L101-L108

@bdunogier WDYT?

@emodric
Copy link
Collaborator Author

emodric commented Jan 12, 2017

@wizhippo Your input is appreciated too :)

@wizhippo
Copy link
Contributor

@emodric I believe that should be able to be removed too with no issue as when you use composer to install you are asked to set the secret. I see no need to reset the secret again from the legacy setup wizard.

@bdunogier
Copy link
Member

I agree with you guys.

@emodric
Copy link
Collaborator Author

emodric commented Jan 12, 2017

PR updated to remove the configurator.

@andrerom
Copy link
Contributor

Ping @lolautruche

@andrerom
Copy link
Contributor

From my side +1 but wanted JV's pov

@lolautruche
Copy link
Contributor

Shouldn't we regenerate the secret?

Other than that, +1

@emodric
Copy link
Collaborator Author

emodric commented Jan 13, 2017

Why though?

Initial composer install asks the user to set the secret. Why should legacy bridge install regenerate user set secret?

@bdunogier
Copy link
Member

Initial composer install asks the user to set the secret. Why should legacy bridge install regenerate user set secret?

I think I agree with that.

@lolautruche
Copy link
Contributor

Alright then :-)

@andrerom
Copy link
Contributor

andrerom commented Jan 16, 2017

v1.1.0 or even v2.0 version for this maybe then? Other feature changes we should aim for while at it?

@lolautruche
Copy link
Contributor

I'd say 1.1.0 because it can be a blocker sometimes.

@emodric
Copy link
Collaborator Author

emodric commented Jan 16, 2017

1.1.0 sounds okay. I'd like to push another PR to fix deprecations in YML, after merging this, but before tagging.

@andrerom andrerom merged commit cc938c9 into master Jan 16, 2017
@andrerom andrerom deleted the distribution-bundle-5 branch January 16, 2017 11:37
@lolautruche
Copy link
Contributor

Can this be backported to 5.4 please?

DistributionBudle 3.x is way too old and is causing issues with composer such as:

  PHP Warning:  Module 'sysvshm' already loaded in Unknown on line 0
  PHP Warning:  Module 'tokenizer' already loaded in Unknown on line 0
  PHP Warning:  Module 'wddx' already loaded in Unknown on line 0
  PHP Warning:  Module 'xmlreader' already loaded in Unknown on line 0
  PHP Warning:  Module 'xmlwriter' already loaded in Unknown on line 0
  PHP Warning:  Module 'xsl' already loaded in Unknown on line 0
  PHP Warning:  Module 'zip' already loaded in Unknown on line 0

Thanks :-)

@emodric
Copy link
Collaborator Author

emodric commented Jan 31, 2017

@lolautruche Latest Distribution bundle 4.x works fine :)

@lolautruche
Copy link
Contributor

OK I'll check this out, thanks @emodric

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants